Fictitious Symphony Website
The challenge: This project was an assignment to make mobile and desktop wireframes for a website (from scratch) that sells tickets to multiple events of one kind, such as concerts, exhibits, or sporting events.
I chose to design a symphony website because I have many close friends that play in the symphony. These friends helped me make design decisions discussed later in the wireframes.
Tools: Balsamiq
Additional notes: I referenced the El Paso Symphony Orchestra website (https://www.epso.org) to get a feel for similar websites.
The wireframe comments were written using "we" language to simulate the comments of a design team. I did all of the work for this assignment.
I wanted the site to be simple and to the point. The slideshow would house images from the different symphony events; showcasing interesting shots from different performances to catch the user's interest. The tickets to upcoming events are also displayed on the homepage so users can easily jump to upcoming events. Learning about events and buying tickets are major user goals for the Fictitious Symphony Orchestra site.
I developed the desktop wireframes first then made concise versions in the mobile wireframes. These wireframes were based off of the site plan.
This symphony website featured four event types: operas, musicals, symphonies, and pop homages. One of my contacts from the symphony helped me narrow my events down to these four categories. The event type "pop homage" was inspired by the El Paso Symphony's dedication to Selena (playing her music) and the symphony's performance of the music from the Pixar movie Coco.
Before the wireframes, I created site plans to lay out the pages that would make up the Fictitious Symphony website. Some of the pages for the site plan were based on pages from the El Paso Symphony Orchestra website.
The feedback I received from my professor for the first version of the site plan was to have the checkout process appear once and have the different event pages connect to that checkout page. The other critique that I got was to show that there were multiple "products" (event showings) on each event page.
The critique for this iteration was that I should keep in mind that this was not a user flow; not all connections (lines) were necessary for a site plan.
For the final site plan, I ensured to incorporate all previous feedback; having one checkout for all four events to connect to, and reducing the connections to make the plan less cluttered.
If you would like to see all scenes from the wireframes, please contact me via email at heydarianc@gmail.com
Thank you.